Wow! cool!
It would be nice if you also add some small README file on how to build it or plain "make install" will be enough?

Very nice tool! I would like one thing to be clarified, regarding SPIFFS file names. Some environments where SPIFFS is used assume that all file names stored in SPIFFS start with a leading path separator (usually /). In other environments names don't start with the leading slash.
It would be nice if this could be made configurable in the fuse driver.

@benpicco, ah - I must mention, that I just recently finished a fuse wrapper for 0.4.0. Resides only on my computer right now though. Perhaps it is time putting up a devbranch on spiffs.
Nevertheless, I'll look things through.
@igrr good catch. Need to handle that in my version of it also.

@valkuc just run make in the src/fuse directory. You have to provide a spiffs_config.h. If you want to use the one from the default/ folder, just run make TEST=1.

Then you can run mount.spiffs <image> <mount moint> to mount an image (or add -c <size> to create one).

There is no install target, but you can put the executable wherever you want.

@igrr That'd be quite easy I guess, now I'm just always discarding the leading path separator I get from fuse as I've never used them on my fs. It'd be quite trivial to make that configurable.

But does it even still make sense to maintain this if there is an official version from @pellepl coming soon? Maybe just for the 0.3.x branch?

Hi, this tool would be really useful for some of the work I do, but I'm unable to get my spiffs image to mount. Does it still work? I'm working on macos.